Add data-driven utility for automatic relay configuration#66
Add data-driven utility for automatic relay configuration#66
Conversation
Remove extra fields from Relay, dead code, and add copyright headers.
|
David Shoots seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
tsachiherman
left a comment
tsachiherman
left a comment
There was a problem hiding this comment.
looks good, one comment -
we. need to get rid of the zoneid; we should use the email/authkey + domainArgs to discover it dynamically and use it.
A misconfigured mismatch between the zoneid and domainArgs would Create a sub-domain under the zoneid, which is not what we want.
The functionality to extract the zoneid from the email/keyauth is already used in algons.
Can you make those change in this PR? |
Debugger: Use ledger.appLedger in tealdbg
basic p2p network test
3 participants
This adds a tool
algorelaythat is used for checking and updating Relay configurations in DNS based on our process for mainnet. The tool works against a JSON input file providing details about relays that should be configured, and details about their configuration.For production, this is paired with the foundation's
afdb1 relaycommand.